Method and system for forecasting telephony traffic trends using local number portability databases

ABSTRACT

A method and system for forecasting telephony traffic trends on a network of a given service provider includes storing local number portability (LNP) record portions in a LNP database. Each LNP record portion contains information regarding a corresponding telephone number having been ported between service providers. First and second images of the LNP database are obtained at first and second times. The first and second images are indicative of all the LNP record portions stored in the LNP database at the first and second times. The images are compared to determine migration of the ported telephone numbers between the service providers over a time period between the first and second times. Movement of telephone traffic on the network of the given service provider after the second time is then forecasted as a function of the determined migration of the ported telephone numbers between the service providers.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to methods and systems usinglocal number portability (LNP) databases and, more particularly, to amethod and system for forecasting telephony traffic trends using LNPdatabases.

2. Background Art

Local number portability (LNP) allows wireless and landline telephonecustomers to keep their telephone numbers when they change residencesand/or service providers. A LNP database stores a list of telephonenumbers that have been switched or ported from one service provider toanother service provider. For each ported telephone number, the LNPdatabase also stores an associated location routing number (LRN). Thenetworks of the service providers use the LRN to route a telephone callfrom a point of origination (such as from a telephone associated withthe ported telephone number or from another party's telephone) to apoint of destination (such as to the other one of the telephoneassociated with the ported telephone number or to the other party'stelephone) over the public switched telephone network (PSTN).

Porting telephone numbers between service providers causes changes inthe way that the networks of the service providers handle telephonecalls associated with the ported telephone numbers. Generally, thenetwork of a service provider handles more telephone calls if there is anet influx of ported telephone numbers to the service provider. As such,the service provider should ensure that its network has enough capacityand is properly connected to the networks of other service providers inorder to handle the additional telephone traffic. Likewise, the networkof a service provider handles less telephone calls if there is a netoutflow of ported telephone numbers from the service provider. As such,this service provider should consider changing its network andreconfiguring how its network is connected to the networks of otherservice providers in view of the reduced amount of telephone traffic.

The networks of the other service providers not directly involved in theporting of telephone numbers between two service providers may alsohandle telephone calls associated with the ported telephone numbersdifferently after these telephone numbers have been ported between thetwo directly involved service providers. As such, these other serviceproviders should consider changing their networks and reconfiguring howtheir networks connect with the networks of other service providers inview of the differently routed telephone traffic.

Presently, network engineers monitor service provider networks usingbroad measures such as minutes of use on trunk groups, blocking on trunkgroups, and point-to-point telephone traffic flows through the networks.These metrics are compiled over long periods of time (for instance,several months) and therefore are indicative of what has previouslyhappened in the networks. As such, these are lagging indicators oftelephone traffic trends.

Thus, there exists a need for using LNP database images or snapshotsobtained at periodic times to track ported telephone numbers betweenservice providers and then use this data along with topology andinterconnection data regarding the networks of the service providers inorder to predict future telephone traffic on the service providernetworks.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is pointed out with particularity in the appendedclaims. However, other features of the present invention will becomemore apparent, and the present invention will be best understood byreferring to the following detailed description in conjunction with theaccompanying drawings in which:

FIG. 1 illustrates a flowchart describing the overall operation of amethod in accordance with an embodiment of the present invention;

FIG. 2 illustrates a segment of the public switched telephone network(PSTN) in accordance with the present invention; and

FIG. 3 illustrates a block diagram of old and new ported serviceprovider networks in accordance with the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

Referring now to FIG. 1, a flowchart describing the overall operation ofa method 10 in accordance with an embodiment of the present invention isshown. In general, method 10 provides a service provider with theability to forecast telephony traffic trends in the public switchedtelephone network (PSTN) using local number portability (LNP) databases.Method 10 includes periodically obtaining LNP database images orsnapshots. The images are then compared with one another to determinethe service providers (i.e., carriers) from which ported telephonenumbers have migrated to and from over time. That is, the images arecompared with one another to determine the service providers from whichported telephone numbers have migrated over a period of time, and todetermine the service providers to which the ported telephone numbershave migrated over the period of time. The service providers then usethis information in conjunction with information known about theirnetworks in order to forecast where telephony traffic will migrate to intheir networks as a result of telephone numbers having been portedbetween the service providers.

This network engineering capability provided by method 10 makestelephone traffic engineering more immediate than the use of laggingindicators. Accordingly, this network engineering capability assists inanticipating telephone traffic changes brought about with the advent ofwireless number portability. The porting impact of wireless numberportability is expected to be substantial and therefore markedly changetelephone traffic patterns. Using ported telephone number changes in theLNP database in accordance with method 10 greatly shortens the timeframe for determining telephone traffic shifts in the PSTN brought aboutwith the advent of wireless number portability. In summary, method 10uses telephone number movement between service providers to forecastassociated telephone traffic trends, whereas other methods look afterthe fact how the actual telephone traffic has shifted.

As shown in FIG. 1, method 10 includes a service provider obtaining afirst image or snapshot of a LNP database at a given first time as shownin block 12. The image or snapshot of the LNP database may be obtainedfrom the LNP database itself or from a local service management system(LSMS). The LSMS has a copy of the LNP database and other relatedinformation. The LNP database stores a list of telephone numbers thathave been ported between service providers. A telephone number ported toa service provider means that the user of the ported telephone number isa customer or subscriber of the service provider. As such, the serviceprovider of which the telephone number has ported to becomes associatedwith the ported telephone number. That is, the customer of the telephonenumber becomes a customer of the service provider once the customer'stelephone number has been ported to this service provider.

For each ported telephone number, the LNP database also stores anassociated location routing number (LRN) and other signalinginformation. The service providers use the LRN and the signalinginformation in order to complete telephone calls over the PSTN involvingthe associated ported telephone number. In order to obtain the firstimage of the LNP database, a switch of the service provider sends aquery to the LNP database itself for the first image at the first time.The first image of the LNP database provides information indicative ofthe ported telephone numbers at the first time. The service providersassociated with the ported telephone numbers at the first time aredeterminable by using the associated LRNs. Alternatively, a processor ofthe service provider sends a query to the LSMS for a copy of the firstimage of the LNP database and the related information. The relatedinformation generally includes transaction histories of the portedtelephone numbers along with the identities of the service providersinvolved with the porting during each transaction.

Method 10 then includes the service provider obtaining a second image orsnapshot (as well as other subsequent images or snapshots) of the LNPdatabase at a second subsequent time (and other subsequent times) asshown in block 14. The service provider obtains the second andsubsequent images periodically at subsequent times by having its switchsend queries to the LNP database. Alternately, the processor of theservice provider sends queries to the LSMS. These subsequent images ofthe LNP database provide information indicative of the ported telephonenumbers at the subsequent times. Again, the service providers associatedwith the ported telephone numbers at the subsequent times aredeterminable by using the associated LRNs (or determinable directly fromthe related information stored in the LSMS).

Method 10 then includes the service provider comparing the first andsecond images (as well as other subsequent images) to one another inorder to determine migration of the ported telephone numbers between theservice providers during the time period between the first and secondtimes as shown in block 16. The comparison yields information regardingfrom and to which service providers the ported telephone numbers havemigrated by the end of the associated time period. Method 10 thenincludes the service provider aggregating this comparison information tothe service provider level as shown in block 18. The aggregatedcomparison information provides information indicative of which portedtelephone numbers have migrated from the service provider during thetime period, and information indicative of which ported telephonenumbers have migrated to the service provider during the time period.

Method 10 then includes combining the aggregated comparison informationwith information already known about the network of the service provideras shown in block 20. In addition to information regarding the assignedcapacity and configuration of the elements of the network of the serviceprovider and other types of related network information, such knownnetwork information also includes information about how the network ofthe service provider connects with the networks of other serviceproviders.

Based on the combined information generated in block 20, method 10 thenforecasts where telephone traffic will migrate to in the network of theservice provider as shown in block 22. The telephone traffic forecast isessentially based on the ported telephone number movement between theservice providers from the first to the second time (as well as beingbased on the known network information). As such, the telephone trafficforecast will forecast where telephone traffic will migrate to in thenetwork of the service provider after the second (and subsequent)time(s) as a result of the ported telephone numbers.

Referring now to FIG. 2, with continual reference to FIG. 1, a PSTNsegment 30 for use with method 10 is shown. PSTN segment 30 includes LNPdatabases 34 a, 34 b, and 34 c, which are associated with a plurality ofrespective service providers (i.e., carriers). The service providersgenerally include local exchange carriers (LECs), cellular carriers(CMRS), and inter-exchange carriers (IXCs). PSTN segment 30 includesservice providers LEC-1 36 a, LEC-2 36 b, LEC-3 38 c, and LEC-4 38 d;service provider CMRS-1 38; and service providers IXC-1 40 a and IXC-240 b. As such, PSTN segment 30 is serviced by four service provider LECs(36 a, 36 b, 36 c, and 38 d), one service provider CMRS 38, and twoservice provider IXCs (40 a and 40 b). The service provider LECs 36 andCMRS 38 provide regional telephone services to their customers. Theservice provider IXC 40 operate with the service provider LECs 36 andCMRS 38 to provide long distance telephone services to their customers.The service providers LECs 36, CMRS 38, and IXCs 40 include switches forrouting the telephone calls.

Some service providers are in communication with LNP databases 34 inorder to provide LNP functionality. For instance, service provider LEC-136 a is in communication with LNP database 34 b; and service providersLEC-2 36 b and LEC-4 36 d are in communication with LNP database 34 c.Service provider LEC-3 36 c does not have communication with an LNPdatabase and is unable by itself to support LNP. The service providerscommunicate in real time with LNP databases 34 to receive LRNinformation for routing telephone calls involving the ported telephonenumbers over the PTSN.

The service providers provide telephone services to land line telephonesand wireless phones of their customers. The customers of the serviceproviders have their own associated telephone numbers. For example, thecustomer of telephone 42 a (number 816-724-3348) is a customer ofservice provider LEC-1 36 a; the customers of telephones 42 b and 42 c(numbers 816-724-2245 and 816-662-3378) are the customers of serviceprovider LEC-2 36 b; the customer of telephone 42 d (number507-863-2112) is a customer of service provider LEC-3 36 c; and thecustomer of telephone 42 e (number 816-845-1221) is a customer ofservice provider LEC-4 36 d. Similarly, the customer of wireless phone44 (number 816-234-7711) is a customer of service provider CMRS-1 38.

In PSTN segment 30, the service provider LECs 36 and the serviceprovider CMRS 40 are assumed to be in a ported area. As customers portbetween service providers, the existing trunk arrangements can becomeinsufficient to serve the rearranged traffic patterns generated by theported customers. This results in blocked telephone calls or intelephone calls using higher cost and less efficient routes in thenetworks to get from the network of one service provider to the networkof another service provider.

As an example of the rearranged traffic patterns when customers portbetween service providers, assume that customer of telephone 42 b makesmany telephone calls to the customer of telephone 42 c. Both of thesecustomers are served by the switches of service provider LEC-2 36 b. Assuch, no other service provider sees the telephone traffic for thetelephone calls between telephones 42 b and 42 c because such telephonetraffic occurs entirely within service provider LEC-2 36 b. Now assumethat the customer of telephone 42 b ports to service provider CMRS-1 38and continues to make many telephone calls to telephone 42 c. Nowservice provider CMRS-1 38, in addition to service provider LEC-2 36 b,sees the telephone traffic between telephones 42 b and 42 c.Furthermore, there are no direct connections between service providerCMRS-1 38 and LEC-2 36 b. As such, the telephone calls betweentelephones 42 b and 42 c are likely to tandem through a switch ofservice provider LEC-1 36 a. Accordingly, the switches of serviceproviders LEC-1 36 a, LEC-2 36 b, and CMRS-1 38 are impacted by thetelephone traffic between telephones 42 b and 42 c as a result of thecustomer of telephone 42 b porting from service provider LEC-2 36 b toservice provider CMRS-1 38.

In accordance with method 10, a switch of service provider LEC-1 36 aaccesses or queries LNP database 34 b to obtain images of the LNPdatabase which includes the LNP record portion that shows the customerof telephone 42 b porting from service provider LEC-2 36 b to serviceprovider CMSR-1 38. Similarly, the service provider LEC-1 36 a receivesLNP record portions from the images of LNP database 34 b of all theporting events that occur in its serving area. By analyzing the LNPrecord portions in order to determine how customers are moving betweenthe service providers, service provider LEC-1 36 a is able to identifytelephone traffic patterns and trends. Based on these patterns andtrends, service provider LEC-1 36 a is better prepared to manage itsnetwork as well as its network connections to the networks of the otherservice providers.

In conjunction with the information regarding how customers are movingbetween the service providers, service provider LEC-1 36 a usesinformation known about its network to manage its network accordingly.Such known information includes information regarding where the networkof service provider LEC-1 36 a will route telephone calls. That is, theknown information includes information of which elements of the networkof service provider LEC-1 36 a will be used to complete telephone calls.The known information also includes information of which elements of thenetwork of service provider LEC-1 36 a will be used to completetelephone calls if the corresponding telephone numbers have been ported.

Referring now to FIG. 3, with continual reference to FIGS. 1 and 2, ablock diagram 50 of old and new service provider networks 52 and 54 inaccordance with the method of the present invention is shown. Old andnew service provider networks 52 and 54 are in communication with anumber portability administration/service management system (NPAC SMS)32. The old service provider is “old” in the sense that a customer hasdiscontinued service with the old service provider. That is, thecustomer's telephone number has ported out from the old service providerto the new service provider. The new service provider is “new” in thesense that the customer has started service with the new serviceprovider. That is, the customer's telephone number has been ported tothe new service provider from the old service provider.

Old and new service provider networks 52 and 54 generally include thesame elements for carrying out the LNP functionality and for enteringand submitting service order changes to NPAC SMS 32. For instance, oldservice provider network 52 includes a local service management system(LSMS) 56 a, a service order administration (SOA) 58 a, a regional LNPdatabase 60 a, a local service request (LSR) 62 a, and a service orderentry (SOE)/billing system 64 a. Likewise, new service provider network54 includes a LSMS 56 b, a SOA 58 b, a regional LNP database 60 b, a LSR62 b, and a SOE/billing system 64 b.

Block diagram 50 illustrates the general flow for the LNP records andLNP record portions required in each network 52 and 54 in order tocomplete telephone calls involving ported telephone numbers. The old andnew service providers both submit records regarding the customer to portto the neutral NPAC SMS 32. At the time the porting event occurs and thecustomer's service is moved from the old service provider to the newservice provider, NPAC SMS 32, downloads a LNP record for the portingcustomer to LSMS 56 a and LSMS 56 b as well as to the LSMS of otherservice providers serving that area. The LNP record for a portedtelephone number includes a history file of all transactions related tothe ported telephone number including the LRN and the identity of theinvolved service providers. These other service providers are notdirectly involved in the porting as are the old or new serviceproviders. LSMS 56 a and LSMS 56 b download a portion of the LNP record(i.e., the LNP record portion) to their respective LNP databases 60 aand 60 b. As indicated above, the LNP record portion includes the portedtelephone number, the LRN for the ported telephone number, and othersignaling information.

In order to complete a telephone call involving a ported telephonenumber, LNP databases 60 are consulted in real-time in order to obtainthe corresponding LRN from the LNP databases. For example, network 54 ofthe new service provider includes a tandem switch 66 and an end officeswitch 68 which are both connected by signal transfer points (STPs) 70to LNP database 60 b. Either one or both of tandem and end officeswitches 66 and 68 consult LNP database 60 b via STPs 70 in order toroute telephone calls of the customer to network 54 of the new serviceprovider. End office switch 68 is also operable to query LNP database 60b to obtain images of the LNP database in accordance with method 10.

Old and new service provider networks 52 and 54 each further includerespective processors 72 a and 72 b. Processor 72 a is in communicationwith LSMS 56 a and processor 72 b is in communication with LSMS 56 b.Each processor 72 a and 72 b is operable to extract from the respectiveLSMS 56 a and LSMS 56 b copies of the respective LNP databases (60 a, 60b) and the other related information. The other related informationincludes the identity of the service providers involved with portedtelephone numbers. By extracting and analyzing this informationtransmitted from NPAC SMS 32 to the respective LSMS 56 a and LSMS 56 bin accordance with method 10, the old and new service providers identifypatterns and trends of how customers are moving between the serviceproviders. That is, processor 72 a of the old service provider obtainsimages or snapshots of LSMS 56 a (as opposed to obtaining images orsnapshots of the LNP record portions stored in LNP database 60 a) inaccordance with method 10 in order to determine which telephone numbershave ported over time and to determine the identity of the involvedservice providers. In turn, the old service provider uses thisinformation with information already known about network 52 in order todetermine the impacts of those trends on network 52 as well as theimpact of those trends on the service providers in general.

Similarly, processor 72 b of the new service provider obtains images orsnapshots of LSMS 56 b (as opposed to obtaining images or snapshots ofthe LNP record portions stored in LNP database 60 b) in accordance withmethod 10 in order to determine which telephone numbers have ported overtime and to determine the identity of the involved service providers.With this information and information known about network 54, the newservice provider determines the impacts of those trends on network 54 aswell as the impact of those trends on the service providers in general.

Thus, it is apparent that there has been provided, in accordance withthe present invention, a method and system for forecasting telephonytraffic trends using LNP databases that fully satisfy the objects, aims,and advantages set forth above. While embodiments of the presentinvention have been illustrated and described, it is not intended thatthese embodiments illustrate and describe all possible forms of thepresent invention. Rather, the words used in the specification are wordsof description rather than limitation, and it is understood that variouschanges may be made without departing from the spirit and scope of thepresent invention.

1. A method for forecasting telephony traffic trends on a network of agiven service provider, the method comprising: storing local numberportability (LNP) record portions in a LNP database, each LNP recordportion containing information regarding a corresponding telephonenumber having been ported between service providers; obtaining a firstimage of the LNP database at a first time, the first image beingindicative of the LNP record portions stored in the LNP database at thefirst time; obtaining a second image of the LNP database at a secondtime subsequent to the first time, the second image being indicative ofthe LNP record portions stored in the LNP database at the second time;comparing the images of the LNP database to determine migration of theported telephone numbers between the service providers over a timeperiod between the first and second times; and forecasting movement oftelephone traffic on the network of the given service provider after thesecond time as a function of the determined migration of the portedtelephone numbers between the service providers.
 2. The method of claim1 further comprising: combining information indicative of the determinedmigration of the ported telephone numbers between the service providerswith known information about the network of the given service provider;wherein forecasting includes forecasting movement of telephone trafficon the network of the given service provider as a function of thecombined information.
 3. The method of claim 2 wherein: the knowninformation includes known information regarding how the network of thegiven service provider is connected to the networks of the other serviceproviders.
 4. The method of claim 1 wherein the network of the givenservice provider includes a switch, wherein: obtaining the first andsecond images of the LNP database includes the switch of the network ofthe given service provider querying the LNP database for the images. 5.The method of claim 1 wherein: each LNP record portion containsinformation regarding a corresponding ported telephone number and alocation routing number (LRN) for the ported telephone number; themethod further comprising determining the identity of the serviceproviders directly involved with the determined migration of the portedtelephone numbers using the LRNs for the ported telephone numbers;wherein forecasting includes forecasting movement of telephone trafficon the network of the given service provider after the second time as afunction of the determined migration of the ported telephone numbersbetween the service providers and the determined identity of the serviceproviders directly involved with the determined migration.
 6. The methodof claim 1 further comprising: obtaining a third image of the LNPdatabase at a third time subsequent to the first and second times, thethird image being indicative of the LNP record portions stored in theLNP database at the third time; wherein comparing includes comparing theimages of the LNP database to determine migration of the portedtelephone numbers between the service providers over a time periodbetween the first and third times; wherein forecasting includesforecasting movement of telephone traffic on the network of the givenservice provider after the third time as a function of the determinedmigration of the ported telephone numbers between the service providersover the time period between the first and second times.
 7. The methodof claim 1 further comprising: configuring the network of the givenservice provider based on the forecasted movement of telephone trafficon the network of the given service provider.
 8. A system forforecasting telephony traffic trends on a network of a given serviceprovider, the system comprising: a local number portability (LNP)database having stored LNP record portions, each LNP record portioncontaining information regarding a corresponding telephone number havingbeen ported between service providers; a switch in the network of thegiven service provider, the switch being in communication with the LNPdatabase; the switch querying the LNP database to obtain a first imageof the LNP database at a first time, the first image being indicative ofthe LNP record portions stored in the LNP database at the first time;the switch querying the LNP database to obtain a second image of the LNPdatabase at a second time subsequent to the first time, the second imagebeing indicative of the LNP record portions stored in the LNP databaseat the second time; the given service provider comparing the images ofthe LNP database obtained by the switch to determine migration of theported telephone numbers between the service providers over a timeperiod between the first and second times, and then the given serviceprovider forecasting movement of telephone traffic on the network of thegiven service provider after the second time as a function of thedetermined migration of the ported telephone numbers between the serviceproviders.
 9. The system of claim 8 further comprising: a local servicemanagement system (LSMS) in communication with the LNP database, theLSMS storing LNP records containing the information regardingcorresponding telephone numbers having been ported between the serviceproviders and the identity of the service providers directly involved inthe porting of the corresponding telephone numbers, wherein the LSMSprovides a LNP record of a corresponding ported telephone number to theLNP database when the corresponding telephone number has been portedbetween service providers.
 10. The system of claim 9 further comprising:a processor in the network of the given service provider, the processorquerying the LSMS to obtain a third image of the LNP database at a thirdtime subsequent to the second time, the third image being indicative ofthe LNP record portions stored in the LNP database at the third time;the given service provider comparing the images of the LNP databaseobtained by the switch and the processor to determine migration of theported telephone numbers between the service providers over a timeperiod between the first and third times, and then the given serviceprovider forecasting movement of telephone traffic on the network of thegiven service provider after the third time as a function of thedetermined migration of the ported telephone numbers between the serviceproviders between the first and third times.
 11. The system of claim 10wherein: each LNP record portion contains information regarding acorresponding ported telephone number and a location routing number(LRN) for the ported telephone number; wherein the given serviceprovider determines the identity of the service providers directlyinvolved with the determined migration of the ported telephone numbersusing the LRNs for the ported telephone numbers, and then the givenservice provider forecasts movement of telephone traffic on the networkof the given service provider after the second time as a function of thedetermined migration of the ported telephone numbers between the serviceproviders and the determined identity of the service providers directlyinvolved with the determined migration.
 12. A method for forecastingtelephony traffic trends on a network of a given service provider, themethod comprising: storing local number portability (LNP) records in alocal service management system (LSMS), each LNP record containinginformation regarding a corresponding telephone number having beenported between service providers and the identities of the serviceproviders involved in the porting of the corresponding telephone number;obtaining a first image of the LSMS at a first time, the first image ofthe LSMS being indicative of the LNP records stored in the LSMS at thefirst time; obtaining a second image of the LSMS at a second timesubsequent to the first time, the second image of the LSMS beingindicative of the LNP records stored in the LSMS at the second time;comparing the images of the LSMS to determine migration of the portedtelephone numbers between the service providers over a time periodbetween the first and second times; and forecasting movement oftelephone traffic on the network of the given service provider after thesecond time as a function of the determined migration of the portedtelephone numbers between the service providers.
 13. The method of claim12 wherein: comparing includes comparing the images of the LSMS todetermine the identities of the service providers involved in theporting of the ported telephone numbers; wherein forecasting includesforecasting movement of telephone traffic on the network of the givenservice provider as a function of the determined migration of the portedtelephone numbers between the service providers and the determinedidentities of the service providers involved in the porting of theported telephone numbers.
 14. The method of claim 12 further comprising:combining information indicative of the determined migration of theported telephone numbers between the service providers with knowninformation about the network of the given service provider; whereinforecasting includes forecasting movement of telephone traffic on thenetwork of the given service provider as a function of the determinedmigration and the known information.
 15. The method of claim 14 wherein:the known information includes known information regarding how thenetwork of the given service provider is connected to the networks ofthe other service providers.
 16. The method of claim 12 wherein thenetwork of the given service provider includes a processor, wherein:obtaining the first and second images of the LSMS includes the processorof the network of the given service provider querying the LSMS for theimages.
 17. The method of claim 12 further comprising: obtaining a thirdimage of the LSMS at a third time subsequent to the first and secondtimes, the third image of the LSMS being indicative of the LNP recordsstored in the LSMS at the third time; wherein comparing includescomparing the images of the LSMS to determine migration of the portedtelephone numbers between the service providers over a time periodbetween the first and third times; wherein forecasting includesforecasting movement of telephone traffic on the network of the givenservice provider after the third time as a function of the determinedmigration of the ported telephone numbers between the service providers.18. The method of claim 12 further comprising: configuring the networkof the given service provider based on the forecasted movement oftelephone traffic on the network of the given service provider.
 19. Themethod of claim 12 further comprising: storing local number portability(LNP) record portions in a LNP database, each LNP record portioncontaining information regarding a corresponding telephone number havingbeen ported between service providers; obtaining an image of the LNPdatabase at a third time subsequent to the second time, the image of theLNP database being indicative of the LNP record portions stored in theLNP database at the third time; wherein comparing includes comparing theimages of the LSMS and the image of the LNP database to determinemigration of the ported telephone numbers between the service providersover a time period between the first and third times; whereinforecasting includes forecasting movement of telephone traffic on thenetwork of the given service provider after the third time as a functionof the determined migration of the ported telephone numbers between theservice providers over the time period between the first and thirdtimes.
 20. The method of claim 19 further comprising: configuring thenetwork of the given service provider based on the forecasted movementof telephone traffic on the network of the given service provider afterthe third time.